@ObjectMike said in Double NAT, but I have no need to access the inner NAT: you're hosting your workplace's network within your home network? Why...? Because the office space no longer exists and I currently hold what little equipment we managed to recover. The rest of the shit is being held by the place's owner because "show me the contract for this stuff and I'll let you have it" or someshit like that.

@remi True, the bigger problem that caused the big spike here last summer was relaxing the rules too quickly and the 'Dancing with Johnson' campaign, where people were encouraged to get a single-dose Johnson vaccine which allowed them to go partying without tests or other restrictions that same night.

Professor Oddington, a peculiar figure with a long, unkempt beard and wild hair that seemed to defy gravity, stood at the front of his classroom. His eccentricity was notorious within the Hogwarts community, and his lessons were known for their unconventional theories. Today, he was about to introduce his students to a brand new concept: the MagiQuad. "Ahem, attention, class," Professor Oddington said, tapping his wand against the blackboard. "Today, we'll be delving into the realm of the MagiQuad, a groundbreaking magical theory that will revolutionize the way you perceive and practice magic." He drew a large square on the blackboard, dividing it into four smaller squares, each labeled with a distinct aspect: Elemental, Transmutative, Enchantive, and Protective. "You see, the MagiQuad posits that all magic can be classified into these four primary categories, which simultaneously and harmoniously coexist within the magical universe. Each category is inherently linked to the other three, forming an interconnected web of magical energy that powers our spells and enchantments." The students exchanged confused glances but remained silent, knowing that interrupting Professor Oddington was not advisable. "Now, let's explore each aspect of the MagiQuad," he continued. "Elemental magic focuses on harnessing the raw power of the natural world: earth, air, fire, and water. Transmutative magic, on the other hand, deals with altering the properties of objects, beings, or even oneself. Enchantive magic specializes in imbuing items or creatures with magical properties, while Protective magic is centered around shielding and warding off negative energies." Professor Oddington tapped his wand against the blackboard again, and the MagiQuad diagram began to rotate, as if each square was spinning on its axis. "The key to unlocking the true potential of the MagiQuad is understanding the synchronicity between the four categories. When combined, they create a magical synergy that amplifies the power of spells and enchantments, transcending the limitations of traditional magical practice." He paused, allowing the students to absorb the information. "For today's assignment, I want you to experiment with the MagiQuad theory. Choose a spell and try to incorporate at least two aspects of the MagiQuad into your casting. Remember, the key is to find the balance and harmony between the categories, just as they coexist within the magical universe." As the students began to whisper amongst themselves, Professor Oddington smiled, confident that the MagiQuad would challenge their perceptions of magic and inspire them to think outside the confines of traditional magical theory.

@ask_compu said in Forever posting...: @Tsaukpaetra it went through That it did, and it let the other one through right after. I blame websocket reconnection failure.

@Atazhaia said in When your Websocket connection experiences a protocol error: @Tsaukpaetra And I just got a monitor with 10-bit color support and you're telling me I'm supposed to be on 65027-bit color support by now? I feel cheated now! It's cool, they're not supported anymore.

@Gąska said in Re: Go stand behind him: @pie_flavor said in Re: Go stand behind him: @Gąska said in Re: Go stand behind him: @pie_flavor said in Re: Go stand behind him: @Gąska You're missing it. Serialization is done by reflection at runtime. That's bad. Not horrible, but bad (mostly because of performance). Mixins are done by reflection at runtime. That's horrible. Like, actually horrible, worse than not having mixins at all. What the fuck are you on about? What did you think happened in annotation based serialization / mixin systems? It's not done by gremlins. Maybe it's baked on first use and maybe the annotations are reinterpreted each time but there is absolutely no way to do an annotation based system without reflection. Yes there is? Just move the runtime stuff to compile time. Surely it's not hard to imagine. And from what I understood from your rambling about Lombok, it's certainly possible to do all that at compile time in Java. It even makes more sense to do it at compile time than at runtime, since you can type check all the code and make sure everything actually works before the relevant code path even gets run. Moving to runtime the stuff that defines what kinds of operations your class even supports is huge . Not the first time Java turns out to be huge . Again: what are you on about? Example. @Listener goes on a method, and the class that contains it gets registered with the EventManager. Said EventManager figures out that it should wrap the class in an EventListener, and when the listener's invoked, pass the event as the first method argument and various fields inside the event as the remaining arguments. How would you move this to compile-time if, for example, EventListener was not present in the API and the API was supposed to be implementation-agnostic? What I said is that code that compiles with APT processors should not fail to compile without APT processors. But why? There's literally no reason whatsoever to do that. It's like saying that programs using Stream APIs should not fail to compile without Stream APIs present. Annotations aren't APIs. Do they inform external code what kind of operations can be performed on your class? Then they're API. No matter how much you'll ramble about compile time vs. runtime, about APT processors and lack thereof, it all comes down to this one thing. Does the annotation enable your code to be used by external code? Then it's API. The annotation is not what enables your code to be used by external code. My method labeled @Listener can be called by anything. Any class that wants to can call MyPlugin.instance().onInit(new GameInitializationEvent()). The annotation is additional information that the event manager uses to determine that the method should be called when a GameInitializationEvent is posted. If @Listener was knocked off, it would not affect external code's ability to use the method - it would just be a change in metadata. e: Oh yeah, and this ability to dynamically fuck with the AST at compile time is documented but unsupported. It's liable to break any time Oracle feels like it, and in fact Lombok isn't working on Java 9-11 yet.